Computerized systems and methods for managing inventory by determining product prices based on product characteristics

ABSTRACT

Systems and method are provided for managing inventory by determining product prices based on product characteristics. One method includes, based on a condition of the product and an age of the product, determining a new price of a returned product and modifying the database to assign the new price to the product identifier. Based on a determination that the product is not a returned product from a customer: calculating an inventory rate associated with the product; based on the calculated inventory rate, determining a new price of the product; and modifying the database to assign, to the product identifier, the inventory rate and the new price.

Technical Field

The present disclosure generally relates to computerized systems andmethods for managing inventory by determining product prices based onproduct characteristics. In particular, embodiments of the presentdisclosure relate to inventive and unconventional systems that mayautomatically calculate and apply discounts to product prices byautomatically identifying relationships between the age of the productand the condition or the inventory rate of the product.

BACKGROUND

The sale of returned products may be as important as the sale of newproducts for many organizations. The sale of any product may bedifficult or impossible if it is listed at a price that is inconsistentwith the true value of the product. Return processing is costly toorganizations in two ways. The first type of cost relates to shippingand handling costs. The process of reversing an online order has manysteps and includes the cost of the delivery as well as the many touches,each of which comes with a labor cost, to move a return item back intoinventory stored in fulfillment centers. It is inevitable that theexpense will reduce profit margins. The second type of cost is moredifficult to quantify, but the longer a return item stays out ofcirculation and is unable to be sold, the less value it has whichresults in a loss for the retailer. This second type of cost may alsoapply to new products that have never been sold.

Conventional inventory management systems transfer a return item withoutdefects from a return center storing the return item to a fulfillmentcenter for resale at the original price. For example, these conventionalcomputerized systems may only rely on the original price or an arbitrarydiscount to assign a price to returned products or products that havebeen stored in a fulfillment center for a long time. These computerizedsystems do not determine new prices that are consistent with the truevalue of the products.

Therefore, there is a need for improved methods and systems for managinginventory by determining product prices based on productcharacteristics.

SUMMARY

One aspect of the present disclosure is directed to a system formanaging inventory by determining product prices based on productcharacteristics. The system may include a memory storing instructionsand at least one processor configured to execute instructions. Theinstructions may include scanning, via a user device associated with afulfillment center, an indicia of a product; transmitting, via the userdevice, a request for assigning a product price to the product, whereinthe request comprises a product identifier associated with the product;based on the product identifier, searching a database for an originalprice of the product and identifying the original price of the product;retrieving, from the database, the original price of the product; anddetermining, based on the product identifier, whether the product is areturned product from a customer. Based on a determination that theproduct is a returned product from a customer: modifying the database toassign, to the product identifier, the determination that the product isa returned product; determining a condition of the product; determiningan age of the product; modifying the database to assign, to the productidentifier, the condition of the product and the age of the product;based on the condition of the product and the age of the product,determining a new price of the product, wherein the new price is adiscount of the original price; and modifying the database to assign thenew price to the product identifier. Based on a determination that theproduct is not a returned product from a customer: modifying thedatabase to assign, to the product identifier, the determination thatthe product is not a returned product; calculating an inventory rateassociated with the product; based on the calculated inventory rate,determining a new price of the product, wherein the new price is adiscount of the original price; and modifying the database to assign, tothe product identifier, the inventory rate and the new price. Theinstructions further include transmitting a request, to the user device,to list the product for sale at the new price.

Another aspect of the present disclosure is directed to a method formanaging inventory by determining product prices based on productcharacteristics. The method may include scanning, via a user deviceassociated with a fulfillment center, an indicia of a product;transmitting, via the user device, a request for assigning a productprice to the product, wherein the request comprises a product identifierassociated with the product; based on the product identifier, searchinga database for an original price of the product and identifying theoriginal price of the product; retrieving, from the database, theoriginal price of the product; and determining, based on the productidentifier, whether the product is a returned product from a customer.Based on a determination that the product is a returned product from acustomer: modifying the database to assign, to the product identifier,the determination that the product is a returned product; determining acondition of the product; determining an age of the product; modifyingthe database to assign, to the product identifier, the condition of theproduct and the age of the product; based on the condition of theproduct and the age of the product, determining a new price of theproduct, wherein the new price is a discount of the original price; andmodifying the database to assign the new price to the productidentifier. Based on a determination that the product is not a returnedproduct from a customer: modifying the database to assign, to theproduct identifier, the determination that the product is not a returnedproduct; calculating an inventory rate associated with the product;based on the calculated inventory rate, determining a new price of theproduct, wherein the new price is a discount of the original price; andmodifying the database to assign, to the product identifier, theinventory rate and the new price. The method may further includetransmitting a request, to the user device, to list the product for saleat the new price.

Yet another aspect of the present disclosure is directed to a system formanaging inventory by determining product prices based on productcharacteristics. The system may include a memory storing instructionsand at least one processor configured to execute instructions. Theinstructions may include scanning, via a user device associated with afulfillment center, an indicia of a product; transmitting, via the userdevice, a request for assigning a product price to the product, whereinthe request comprises a product identifier associated with the product;based on the product identifier, searching a database for an originalprice of the product and identifying the original price of the product;retrieving, from the database, the original price of the product; anddetermining, based on the product identifier, whether the product is areturned product from a customer. Based on a determination that theproduct is a returned product from a customer: modifying the database toassign, to the product identifier, the determination that the product isa returned product; transmitting a pickup request to a user deviceassociated with an inventory worker to pick up the returned product froma return center and deliver the returned product to the fulfillmentcenter; determining a condition of the product; determining an age ofthe product; modifying the database to assign, to the productidentifier, the condition of the product and the age of the product;based on the condition of the product and the age of the product,determining a new price of the product, wherein the new price is adiscount of the original price; and modifying the database to assign thenew price to the product identifier. Based on a determination that theproduct is not a returned product from a customer: modifying thedatabase to assign, to the product identifier, the determination thatthe product is not a returned product; calculating an inventory rateassociated with the product; based on the calculated inventory rate,determining a new price of the product, wherein the new price is adiscount of the original price; and modifying the database to assign, tothe product identifier, the inventory rate and the new price. Theinstructions further include transmitting a request, to the user device,to list the product for sale at the new price.

Other systems, methods, and computer-readable media are also discussedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations, consistent with the disclosed embodiments.

FIG. 1B depicts a sample Search Result Page (SRP) that includes one ormore search results satisfying a search request along with interactiveuser interface elements, consistent with the disclosed embodiments.

FIG. 1C depicts a sample Single Display Page (SDP) that includes aproduct and information about the product along with interactive userinterface elements, consistent with the disclosed embodiments.

FIG. 1D depicts a sample Cart page that includes items in a virtualshopping cart along with interactive user interface elements, consistentwith the disclosed embodiments.

FIG. 1E depicts a sample Order page that includes items from the virtualshopping cart along with information regarding purchase and shipping,along with interactive user interface elements, consistent with thedisclosed embodiments.

FIG. 2 is a diagrammatic illustration of an exemplary fulfillment centerconfigured to utilize disclosed computerized systems, consistent withthe disclosed embodiments.

FIG. 3 depicts an exemplary network of devices and systems automaticallymanaging inventory by determining product prices based on productcharacteristics, consistent with the disclosed embodiments.

FIG. 4 depicts an exemplary multi-dimensional data structure that mayaccess relationships between the condition of the product and the age ofthe product, consistent with the disclosed embodiments.

FIG. 5 depicts an exemplary multi-dimensional data structure that mayaccess relationships between the inventory rate of the product and theage of the product, consistent with the disclosed embodiments.

FIG. 6 depicts a process for managing inventory by determining productprices based on product characteristics, consistent with the disclosedembodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents and steps illustrated in the drawings, and the illustrativemethods described herein may be modified by substituting, reordering,removing, or adding steps to the disclosed methods. Accordingly, thefollowing detailed description is not limited to the disclosedembodiments and examples. Instead, the proper scope of the invention isdefined by the appended claims.

Embodiments of the present disclosure are directed to systems andmethods configured for managing inventory by determining product pricesbased on product characteristics. The disclosed embodiments are capableof determining whether a product is a returned product from a customer.Based on a determination that the product is a returned product from acustomer, a price determination system may modify a database to assign,to a product identifier, the determination that the product is areturned product.

The price determination system may determine a condition of the productbased on the product identifier. The condition may be one of repackaged,package damaged, refurbished, used best, used good, or used normal. Theprice determination system may modify the database to assign, to theproduct identifier, the condition of the product and the age of theproduct. In some embodiments, a data structure may calculate an optimumdiscount for the product by accessing the relationships between thecondition of the product and the age of the product. The pricedetermination system may access the data structure according to theproduct identifier and determine the new price of the product based onan optimum discount calculated by the data structure. The pricedetermination system may modify the database to assign the new price tothe product identifier and transmit a request to a user device to listthe product for sale at the new price. In some embodiments, the pricedetermination system may automatically transmit a notification to a webserver to list the product for sale at the new price.

Based on a determination that the product is not a returned product froma customer, the price determination system may modify the database toassign, to the product identifier, the determination that the product isnot a returned product. In some embodiments, a data structure maycalculate the inventory rate associated with the product by dividing thequantity of usable inventory by the average daily sales volume. In someembodiments, the data structure may calculate an optimum discount forthe product by accessing the relationships between the inventory rate ofthe product and the age of the product. The price determination systemmay access the data structure according to the product identifier anddetermine the new price of the product based on an optimum discountcalculated by the data structure. The price determination system maymodify the database to assign, to the product identifier, the inventoryrate and the new price and transmit a request to the user device to listthe product for sale at the new price. In some embodiments, the pricedetermination system may automatically transmit a notification to a webserver to list the product for sale at the new price.

Referring to FIG. 1A, a schematic block diagram 100 illustrating anexemplary embodiment of a system comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations is shown. As illustrated in FIG. 1A, system 100 may include avariety of systems, each of which may be connected to one another viaone or more networks. The systems may also be connected to one anothervia a direct connection, for example, using a cable. The depictedsystems include a shipment authority technology (SAT) system 101, anexternal front end system 103, an internal front end system 105, atransportation system 107, mobile devices 107A, 107B, and 107C, sellerportal 109, shipment and order tracking (SOT) system 111, fulfillmentoptimization (FO) system 113, fulfillment messaging gateway (FMG) 115,supply chain management (SCM) system 117, warehouse management system119, mobile devices 119A, 119B, and 119C (depicted as being inside offulfillment center (FC) 200), 3^(rd) party fulfillment systems 121A,121B, and 121C, fulfillment center authorization system (FC Auth) 123,and labor management system (LMS) 125.

SAT system 101, in some embodiments, may be implemented as a computersystem that monitors order status and delivery status. For example, SATsystem 101 may determine whether an order is past its Promised DeliveryDate (PDD) and may take appropriate action, including initiating a neworder, reshipping the items in the non-delivered order, canceling thenon-delivered order, initiating contact with the ordering customer, orthe like. SAT system 101 may also monitor other data, including output(such as a number of packages shipped during a particular time period)and input (such as the number of empty cardboard boxes received for usein shipping). SAT system 101 may also act as a gateway between differentdevices in system 100, enabling communication (e.g., usingstore-and-forward or other techniques) between devices such as externalfront end system 103 and FO system 113.

External front end system 103, in some embodiments, may be implementedas a computer system that enables external users to interact with one ormore systems in system 100. For example, in embodiments where system 100enables the presentation of systems to enable users to place an orderfor an item, external front end system 103 may be implemented as a webserver that receives search requests, presents item pages, and solicitspayment information. For example, external front end system 103 may beimplemented as a computer or computers running software such as theApache HTTP Server, Microsoft Internet Information Services (IIS),NGINX, or the like. In other embodiments, external front end system 103may run custom web server software designed to receive and processrequests from external devices (e.g., mobile device 102A or computer102B), acquire information from databases and other data stores based onthose requests, and provide responses to the received requests based onacquired information.

In some embodiments, external front end system 103 may include one ormore of a web caching system, a database, a search system, or a paymentsystem. In one aspect, external front end system 103 may comprise one ormore of these systems, while in another aspect, external front endsystem 103 may comprise interfaces (e.g., server-to-server,database-to-database, or other network connections) connected to one ormore of these systems.

An illustrative set of steps, illustrated by FIGS. 1B, 1C, 1D, and 1E,will help to describe some operations of external front end system 103.External front end system 103 may receive information from systems ordevices in system 100 for presentation and/or display. For example,external front end system 103 may host or provide one or more web pages,including a Search Result Page (SRP) (e.g., FIG. 1B), a Single DetailPage (SDP) (e.g., FIG. 1C), a Cart page (e.g., FIG. 1D), or an Orderpage (e.g., FIG. 1E). A user device (e.g., using mobile device 102A orcomputer 102B) may navigate to external front end system 103 and requesta search by entering information into a search box. External front endsystem 103 may request information from one or more systems in system100. For example, external front end system 103 may request informationfrom FO System 113 that satisfies the search request. External front endsystem 103 may also request and receive (from FO System 113) a PromisedDelivery Date or “PDD” for each product included in the search results.The PDD, in some embodiments, may represent an estimate of when apackage containing the product will arrive at the user's desiredlocation or a date by which the product is promised to be delivered atthe user's desired location if ordered within a particular period oftime, for example, by the end of the day (11:59 PM). (PDD is discussedfurther below with respect to FO System 113.)

External front end system 103 may prepare an SRP (e.g., FIG. 1B) basedon the information. The SRP may include information that satisfies thesearch request. For example, this may include pictures of products thatsatisfy the search request. The SRP may also include respective pricesfor each product, or information relating to enhanced delivery optionsfor each product, PDD, weight, size, offers, discounts, or the like.External front end system 103 may send the SRP to the requesting userdevice (e.g., via a network).

A user device may then select a product from the SRP, e.g., by clickingor tapping a user interface, or using another input device, to select aproduct represented on the SRP. The user device may formulate a requestfor information on the selected product and send it to external frontend system 103. In response, external front end system 103 may requestinformation related to the selected product. For example, theinformation may include additional information beyond that presented fora product on the respective SRP. This could include, for example, shelflife, country of origin, weight, size, number of items in package,handling instructions, or other information about the product. Theinformation could also include recommendations for similar products(based on, for example, big data and/or machine learning analysis ofcustomers who bought this product and at least one other product),answers to frequently asked questions, reviews from customers,manufacturer information, pictures, or the like.

External front end system 103 may prepare an SDP (Single Detail Page)(e.g., FIG. 1C) based on the received product information. The SDP mayalso include other interactive elements such as a “Buy Now” button, a“Add to Cart” button, a quantity field , a picture of the item, or thelike. The SDP may further include a list of sellers that offer theproduct. The list may be ordered based on the price each seller offerssuch that the seller that offers to sell the product at the lowest pricemay be listed at the top. The list may also be ordered based on theseller ranking such that the highest ranked seller may be listed at thetop. The seller ranking may be formulated based on multiple factors,including, for example, the seller's past track record of meeting apromised PDD. External front end system 103 may deliver the SDP to therequesting user device (e.g., via a network).

The requesting user device may receive the SDP which lists the productinformation. Upon receiving the SDP, the user device may then interactwith the SDP. For example, a user of the requesting user device mayclick or otherwise interact with a “Place in Cart” button on the SDP.This adds the product to a shopping cart associated with the user. Theuser device may transmit this request to add the product to the shoppingcart to external front end system 103.

External front end system 103 may generate a Cart page (e.g., FIG. 1D).The Cart page, in some embodiments, lists the products that the user hasadded to a virtual “shopping cart.” A user device may request the Cartpage by clicking on or otherwise interacting with an icon on the SRP,SDP, or other pages. The Cart page may, in some embodiments, list allproducts that the user has added to the shopping cart, as well asinformation about the products in the cart such as a quantity of eachproduct, a price for each product per item, a price for each productbased on an associated quantity, information regarding PDD, a deliverymethod, a shipping cost, user interface elements for modifying theproducts in the shopping cart (e.g., deletion or modification of aquantity), options for ordering other product or setting up periodicdelivery of products, options for setting up interest payments, userinterface elements for proceeding to purchase, or the like. A user at auser device may click on or otherwise interact with a user interfaceelement (e.g., a button that reads “Buy Now”) to initiate the purchaseof the product in the shopping cart. Upon doing so, the user device maytransmit this request to initiate the purchase to external front endsystem 103.

External front end system 103 may generate an Order page (e.g., FIG. 1E)in response to receiving the request to initiate a purchase. The Orderpage, in some embodiments, re-lists the items from the shopping cart andrequests input of payment and shipping information. For example, theOrder page may include a section requesting information about thepurchaser of the items in the shopping cart (e.g., name, address, e-mailaddress, phone number), information about the recipient (e.g., name,address, phone number, delivery information), shipping information(e.g., speed/method of delivery and/or pickup), payment information(e.g., credit card, bank transfer, check, stored credit), user interfaceelements to request a cash receipt (e.g., for tax purposes), or thelike. External front end system 103 may send the Order page to the userdevice.

The user device may enter information on the Order page and click orotherwise interact with a user interface element that sends theinformation to external front end system 103. From there, external frontend system 103 may send the information to different systems in system100 to enable the creation and processing of a new order with theproducts in the shopping cart.

In some embodiments, external front end system 103 may be furtherconfigured to enable sellers to transmit and receive informationrelating to orders.

Internal front end system 105, in some embodiments, may be implementedas a computer system that enables internal users (e.g., employees of anorganization that owns, operates, or leases system 100) to interact withone or more systems in system 100. For example, in embodiments wheresystem 100 enables the presentation of systems to enable users to placean order for an item, internal front end system 105 may be implementedas a web server that enables internal users to view diagnostic andstatistical information about orders, modify item information, or reviewstatistics relating to orders. For example, internal front end system105 may be implemented as a computer or computers running software suchas the Apache HTTP Server, Microsoft Internet Information Services(IIS), NGINX, or the like. In other embodiments, internal front endsystem 105 may run custom web server software designed to receive andprocess requests from systems or devices depicted in system 100 (as wellas other devices not depicted), acquire information from databases andother data stores based on those requests, and provide responses to thereceived requests based on acquired information.

In some embodiments, internal front end system 105 may include one ormore of a web caching system, a database, a search system, a paymentsystem, an analytics system, an order monitoring system, or the like. Inone aspect, internal front end system 105 may comprise one or more ofthese systems, while in another aspect, internal front end system 105may comprise interfaces (e.g., server-to-server, database-to-database,or other network connections) connected to one or more of these systems.

Transportation system 107, in some embodiments, may be implemented as acomputer system that enables communication between systems or devices insystem 100 and mobile devices 107A-107C. Transportation system 107, insome embodiments, may receive information from one or more mobiledevices 107A-107C (e.g., mobile phones, smart phones, PDAs, or thelike). For example, in some embodiments, mobile devices 107A-107C maycomprise devices operated by delivery workers. The delivery workers, whomay be permanent, temporary, or shift employees, may utilize mobiledevices 107A-107C to effect delivery of packages containing the productsordered by users. For example, to deliver a package, the delivery workermay receive a notification on a mobile device indicating which packageto deliver and where to deliver it. Upon arriving at the deliverylocation, the delivery worker may locate the package (e.g., in the backof a truck or in a crate of packages), scan or otherwise capture dataassociated with an identifier on the package (e.g., a barcode, an image,a text string, an RFID tag, or the like) using the mobile device, anddeliver the package (e.g., by leaving it at a front door, leaving itwith a security guard, handing it to the recipient, or the like). Insome embodiments, the delivery worker may capture photo(s) of thepackage and/or may obtain a signature using the mobile device. Themobile device may send information to transportation system 107including information about the delivery, including, for example, time,date, GPS location, photo(s), an identifier associated with the deliveryworker, an identifier associated with the mobile device, or the like.Transportation system 107 may store this information in a database (notpictured) for access by other systems in system 100. Transportationsystem 107 may, in some embodiments, use this information to prepare andsend tracking data to other systems indicating the location of aparticular package.

In some embodiments, certain users may use one kind of mobile device(e.g., permanent workers may use a specialized PDA with custom hardwaresuch as a barcode scanner, stylus, and other devices) while other usersmay use other kinds of mobile devices (e.g., temporary or shift workersmay utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user witheach device. For example, transportation system 107 may store anassociation between a user (represented by, e.g., a user identifier, anemployee identifier, or a phone number) and a mobile device (representedby, e.g., an International Mobile Equipment Identity (IMEI), anInternational Mobile Subscription Identifier (IMSI), a phone number, aUniversal Unique Identifier (UUID), or a Globally Unique Identifier(GUID)). Transportation system 107 may use this association inconjunction with data received on deliveries to analyze data stored inthe database in order to determine, among other things, a location ofthe worker, an efficiency of the worker, or a speed of the worker.

Seller portal 109, in some embodiments, may be implemented as a computersystem that enables sellers or other external entities to electronicallycommunicate with one or more systems in system 100. For example, aseller may utilize a computer system (not pictured) to upload or provideproduct information, order information, contact information, or thelike, for products that the seller wishes to sell through system 100using seller portal 109.

Shipment and order tracking system 111, in some embodiments, may beimplemented as a computer system that receives, stores, and forwardsinformation regarding the location of packages containing productsordered by customers (e.g., by a user using devices 102A-102B). In someembodiments, shipment and order tracking system 111 may request or storeinformation from web servers (not pictured) operated by shippingcompanies that deliver packages containing products ordered bycustomers.

In some embodiments, shipment and order tracking system 111 may requestand store information from systems depicted in system 100. For example,shipment and order tracking system 111 may request information fromtransportation system 107. As discussed above, transportation system 107may receive information from one or more mobile devices 107A-107C (e.g.,mobile phones, smart phones, PDAs, or the like) that are associated withone or more of a user (e.g., a delivery worker) or a vehicle (e.g., adelivery truck). In some embodiments, shipment and order tracking system111 may also request information from warehouse management system (WMS)119 to determine the location of individual products inside of afulfillment center (e.g., fulfillment center 200). Shipment and ordertracking system 111 may request data from one or more of transportationsystem 107 or WMS 119, process it, and present it to a device (e.g.,user devices 102A and 102B) upon request.

Fulfillment optimization (FO) system 113, in some embodiments, may beimplemented as a computer system that stores information for customerorders from other systems (e.g., external front end system 103 and/orshipment and order tracking system 111). FO system 113 may also storeinformation describing where particular items are held or stored. Forexample, certain items may be stored only in one fulfillment center,while certain other items may be stored in multiple fulfillment centers.In still other embodiments, certain fulfillment centers may be designedto store only a particular set of items (e.g., fresh produce or frozenproducts). FO system 113 stores this information as well as associatedinformation (e.g., quantity, size, date of receipt, expiration date,etc.).

FO system 113 may also calculate a corresponding PDD (promised deliverydate) for each product. The PDD, in some embodiments, may be based onone or more factors. For example, FO system 113 may calculate a PDD fora product based on a past demand for a product (e.g., how many timesthat product was ordered during a period of time), an expected demandfor a product (e.g., how many customers are forecast to order theproduct during an upcoming period of time), a network-wide past demandindicating how many products were ordered during a period of time, anetwork-wide expected demand indicating how many products are expectedto be ordered during an upcoming period of time, one or more counts ofthe product stored in each fulfillment center 200, which fulfillmentcenter stores each product, expected or current orders for that product,or the like.

In some embodiments, FO system 113 may determine a PDD for each producton a periodic basis (e.g., hourly) and store it in a database forretrieval or sending to other systems (e.g., external front end system103, SAT system 101, shipment and order tracking system 111). In otherembodiments, FO system 113 may receive electronic requests from one ormore systems (e.g., external front end system 103, SAT system 101,shipment and order tracking system 111) and calculate the PDD on demand.

Fulfillment messaging gateway (FMG) 115, in some embodiments, may beimplemented as a computer system that receives a request or response inone format or protocol from one or more systems in system 100, such asFO system 113, converts it to another format or protocol, and forward itin the converted format or protocol to other systems, such as WMS 119 or3^(rd) party fulfillment systems 121A, 121B, or 121C, and vice versa.

Supply chain management (SCM) system 117, in some embodiments, may beimplemented as a computer system that performs forecasting functions.For example, SCM system 117 may forecast a level of demand for aparticular product based on, for example, based on a past demand forproducts, an expected demand for a product, a network-wide past demand,a network-wide expected demand, a count products stored in eachfulfillment center 200, expected or current orders for each product, orthe like. In response to this forecasted level and the amount of eachproduct across all fulfillment centers, SCM system 117 may generate oneor more purchase orders to purchase and stock a sufficient quantity tosatisfy the forecasted demand for a particular product.

Warehouse management system (WMS) 119, in some embodiments, may beimplemented as a computer system that monitors workflow. For example,WMS 119 may receive event data from individual devices (e.g., devices107A-107C or 119A-119C) indicating discrete events. For example, WMS 119may receive event data indicating the use of one of these devices toscan a package. As discussed below with respect to fulfillment center200 and FIG. 2, during the fulfillment process, a package identifier(e.g., a barcode or RFID tag data) may be scanned or read by machines atparticular stages (e.g., automated or handheld barcode scanners, RFIDreaders, high-speed cameras, devices such as tablet 119A, mobiledevice/PDA 119B, computer 119C, or the like). WMS 119 may store eachevent indicating a scan or a read of a package identifier in acorresponding database (not pictured) along with the package identifier,a time, date, location, user identifier, or other information, and mayprovide this information to other systems (e.g., shipment and ordertracking system 111).

WMS 119, in some embodiments, may store information associating one ormore devices (e.g., devices 107A-107C or 119A-119C) with one or moreusers associated with system 100. For example, in some situations, auser (such as a part- or full-time employee) may be associated with amobile device in that the user owns the mobile device (e.g., the mobiledevice is a smartphone). In other situations, a user may be associatedwith a mobile device in that the user is temporarily in custody of themobile device (e.g., the user checked the mobile device out at the startof the day, will use it during the day, and will return it at the end ofthe day).

WMS 119, in some embodiments, may maintain a work log for each userassociated with system 100. For example, WMS 119 may store informationassociated with each employee, including any assigned processes (e.g.,unloading trucks, picking items from a pick zone, rebin wall work,packing items), a user identifier, a location (e.g., a floor or zone ina fulfillment center 200), a number of units moved through the system bythe employee (e.g., number of items picked, number of items packed), anidentifier associated with a device (e.g., devices 119A-119C), or thelike. In some embodiments, WMS 119 may receive check-in and check-outinformation from a timekeeping system, such as a timekeeping systemoperated on a device 119A-119C.

3^(rd) party fulfillment (3PL) systems 121A-121C, in some embodiments,represent computer systems associated with third-party providers oflogistics and products. For example, while some products are stored infulfillment center 200 (as discussed below with respect to FIG. 2),other products may be stored off-site, may be produced on demand, or maybe otherwise unavailable for storage in fulfillment center 200. 3PLsystems 121A-121C may be configured to receive orders from FO system 113(e.g., through FMG 115) and may provide products and/or services (e.g.,delivery or installation) to customers directly. In some embodiments,one or more of 3PL systems 121A-121C may be part of system 100, while inother embodiments, one or more of 3PL systems 121A-121C may be outsideof system 100 (e.g., owned or operated by a third-party provider).

Fulfillment Center Auth system (FC Auth) 123, in some embodiments, maybe implemented as a computer system with a variety of functions. Forexample, in some embodiments, FC Auth 123 may act as a single-sign on(SSO) service for one or more other systems in system 100. For example,FC Auth 123 may enable a user to log in via internal front end system105, determine that the user has similar privileges to access resourcesat shipment and order tracking system 111, and enable the user to accessthose privileges without requiring a second log in process. FC Auth 123,in other embodiments, may enable users (e.g., employees) to associatethemselves with a particular task. For example, some employees may nothave an electronic device (such as devices 119A-119C) and may insteadmove from task to task, and zone to zone, within a fulfillment center200, during the course of a day. FC Auth 123 may be configured to enablethose employees to indicate what task they are performing and what zonethey are in at different times of day.

Labor management system (LMS) 125, in some embodiments, may beimplemented as a computer system that stores attendance and overtimeinformation for employees (including full-time and part-time employees).For example, LMS 125 may receive information from FC Auth 123, WMS 119,devices 119A-119C, transportation system 107, and/or devices 107A-107C.

The particular configuration depicted in FIG. 1 A is an example only.For example, while FIG. 1A depicts FC Auth system 123 connected to FOsystem 113, not all embodiments require this particular configuration.Indeed, in some embodiments, the systems in system 100 may be connectedto one another through one or more public or private networks, includingthe Internet, an Intranet, a WAN (Wide-Area Network), a MAN(Metropolitan-Area Network), a wireless network compliant with the IEEE802.11a/b/g/n Standards, a leased line, or the like. In someembodiments, one or more of the systems in system 100 may be implementedas one or more virtual servers implemented at a data center, serverfarm, or the like.

FIG. 2 depicts a fulfillment center 200. Fulfillment center 200 is anexample of a physical location that stores items for shipping tocustomers when ordered. Fulfillment center (FC) 200 may be divided intomultiple zones, each of which are depicted in FIG. 2. These “zones,” insome embodiments, may be thought of as virtual divisions betweendifferent stages of a process of receiving items, storing the items,retrieving the items, and shipping the items. So while the “zones” aredepicted in FIG. 2, other divisions of zones are possible, and the zonesin FIG. 2 may be omitted, duplicated, or modified in some embodiments.

Inbound zone 203 represents an area of FC 200 where items are receivedfrom sellers who wish to sell products using system 100 from FIG. 1A.For example, a seller may deliver items 202A and 202B using truck 201.Item 202A may represent a single item large enough to occupy its ownshipping pallet, while item 202B may represent a set of items that arestacked together on the same pallet to save space.

A worker will receive the items in inbound zone 203 and may optionallycheck the items for damage and correctness using a computer system (notpictured). For example, the worker may use a computer system to comparethe quantity of items 202A and 202B to an ordered quantity of items. Ifthe quantity does not match, that worker may refuse one or more of items202A or 202B. If the quantity does match, the worker may move thoseitems (using, e.g., a dolly, a handtruck, a forklift, or manually) tobuffer zone 205. Buffer zone 205 may be a temporary storage area foritems that are not currently needed in the picking zone, for example,because there is a high enough quantity of that item in the picking zoneto satisfy forecasted demand. In some embodiments, forklifts 206 operateto move items around buffer zone 205 and between inbound zone 203 anddrop zone 207. If there is a need for items 202A or 202B in the pickingzone (e.g., because of forecasted demand), a forklift may move items202A or 202B to drop zone 207.

Drop zone 207 may be an area of FC 200 that stores items before they aremoved to picking zone 209. A worker assigned to the picking task (a“picker”) may approach items 202A and 202B in the picking zone, scan abarcode for the picking zone, and scan barcodes associated with items202A and 202B using a mobile device (e.g., device 119B). The picker maythen take the item to picking zone 209 (e.g., by placing it on a cart orcarrying it).

Picking zone 209 may be an area of FC 200 where items 208 are stored onstorage units 210. In some embodiments, storage units 210 may compriseone or more of physical shelving, bookshelves, boxes, totes,refrigerators, freezers, cold stores, or the like. In some embodiments,picking zone 209 may be organized into multiple floors. In someembodiments, workers or machines may move items into picking zone 209 inmultiple ways, including, for example, a forklift, an elevator, aconveyor belt, a cart, a handtruck, a dolly, an automated robot ordevice, or manually. For example, a picker may place items 202A and 202Bon a handtruck or cart in drop zone 207 and walk items 202A and 202B topicking zone 209.

A picker may receive an instruction to place (or “stow”) the items inparticular spots in picking zone 209, such as a particular space on astorage unit 210. For example, a picker may scan item 202A using amobile device (e.g., device 119B). The device may indicate where thepicker should stow item 202A, for example, using a system that indicatean aisle, shelf, and location. The device may then prompt the picker toscan a barcode at that location before stowing item 202A in thatlocation. The device may send (e.g., via a wireless network) data to acomputer system such as WMS 119 in FIG. 1A indicating that item 202A hasbeen stowed at the location by the user using device 119B.

Once a user places an order, a picker may receive an instruction ondevice 119B to retrieve one or more items 208 from storage unit 210. Thepicker may retrieve item 208, scan a barcode on item 208, and place iton transport mechanism 214. While transport mechanism 214 is representedas a slide, in some embodiments, transport mechanism may be implementedas one or more of a conveyor belt, an elevator, a cart, a forklift, ahandtruck, a dolly, a cart, or the like. Item 208 may then arrive atpacking zone 211.

Packing zone 211 may be an area of FC 200 where items are received frompicking zone 209 and packed into boxes or bags for eventual shipping tocustomers. In packing zone 211, a worker assigned to receiving items (a“rebin worker”) will receive item 208 from picking zone 209 anddetermine what order it corresponds to. For example, the rebin workermay use a device, such as computer 119C, to scan a barcode on item 208.Computer 119C may indicate visually which order item 208 is associatedwith. This may include, for example, a space or “cell” on a wall 216that corresponds to an order. Once the order is complete (e.g., becausethe cell contains all items for the order), the rebin worker mayindicate to a packing worker (or “packer”) that the order is complete.The packer may retrieve the items from the cell and place them in a boxor bag for shipping. The packer may then send the box or bag to a hubzone 213, e.g., via forklift, cart, dolly, handtruck, conveyor belt,manually, or otherwise.

Hub zone 213 may be an area of FC 200 that receives all boxes or bags(“packages”) from packing zone 211. Workers and/or machines in hub zone213 may retrieve package 218 and determine which portion of a deliveryarea each package is intended to go to, and route the package to anappropriate camp zone 215. For example, if the delivery area has twosmaller sub-areas, packages will go to one of two camp zones 215. Insome embodiments, a worker or machine may scan a package (e.g., usingone of devices 119A-119C) to determine its eventual destination. Routingthe package to camp zone 215 may comprise, for example, determining aportion of a geographical area that the package is destined for (e.g.,based on a postal code) and determining a camp zone 215 associated withthe portion of the geographical area.

Camp zone 215, in some embodiments, may comprise one or more buildings,one or more physical spaces, or one or more areas, where packages arereceived from hub zone 213 for sorting into routes and/or sub-routes. Insome embodiments, camp zone 215 is physically separate from FC 200 whilein other embodiments camp zone 215 may form a part of FC 200.

Workers and/or machines in camp zone 215 may determine which routeand/or sub-route a package 220 should be associated with, for example,based on a comparison of the destination to an existing route and/orsub-route, a calculation of workload for each route and/or sub-route,the time of day, a shipping method, the cost to ship the package 220, aPDD associated with the items in package 220, or the like. In someembodiments, a worker or machine may scan a package (e.g., using one ofdevices 119A-119C) to determine its eventual destination. Once package220 is assigned to a particular route and/or sub-route, a worker and/ormachine may move package 220 to be shipped. In exemplary FIG. 2, campzone 215 includes a truck 222, a car 226, and delivery workers 224A and224B. In some embodiments, truck 222 may be driven by delivery worker224A, where delivery worker 224A is a full-time employee that deliverspackages for FC 200 and truck 222 is owned, leased, or operated by thesame company that owns, leases, or operates FC 200. In some embodiments,car 226 may be driven by delivery worker 224B, where delivery worker224B is a “flex” or occasional worker that is delivering on an as-neededbasis (e.g., seasonally). Car 226 may be owned, leased, or operated bydelivery worker 224B.

Referring to FIG. 3, an exemplary network of devices and systems formanaging inventory by determining product prices based on productcondition is shown. As illustrated in FIG. 3, a system 300 may include aprice determination system 330, which may communicate with a user device320 associated with a user 320A via a network 310. In some embodiments,price determination system 330 may communicate with the other componentsof system 300 via a direct connection, for example, using a cable. Insome other embodiments, system 300 may be a part of system 100 of FIG. 1A and may communicate with the other components of system 100 vianetwork 310 or via a direct connection, for example, using a cable.Price determination system 330 may comprise a single computer or mayeach be configured as a distributed computer system including multiplecomputers that interoperate to perform one or more of the processes andfunctionalities associated with the disclosed examples.

As shown in FIG. 3, price determination system 330 may comprise aprocessor 332, a memory 334, and a database 336. Processor 332 may beone or more known processing devices, such as a microprocessor from thePentium™ family manufactured by Intel™ or the Turion™ familymanufactured by AMD™. Processor 332 may constitute a single core ormultiple core processor that executes parallel processes simultaneously.For example, processor 332 may use logical processors to simultaneouslyexecute and control multiple processes. Processor 332 may implementvirtual machine technologies or other known technologies to provide theability to execute, control, run, manipulate, store, etc. multiplesoftware processes, applications, programs, etc. In another example,processor 332 may include a multiple-core processor arrangementconfigured to provide parallel processing functionalities to allow pricedetermination system 330 to execute multiple processes simultaneously.One of ordinary skill in the art would understand that other types ofprocessor arrangements could be implemented that provide for thecapabilities disclosed herein.

Memory 334 may store one or more operating systems that perform knownoperating system functions when executed by processor 332. By way ofexample, the operating system may include Microsoft Windows, Unix,Linux, Android, Mac OS, iOS, or other types of operating systems.Accordingly, examples of the disclosed invention may operate andfunction with computer systems running any type of operating system.Memory 334 may be a volatile or non-volatile, magnetic, semiconductor,tape, optical, removable, non-removable, or other type of storage deviceor tangible computer readable medium.

Database 336 may include, for example, Oracle™ databases, Sybase™databases, or other relational databases or non-relational databases,such as Hadoop™ sequence files, HBase™, or Cassandra™. Database 336 mayinclude computing components (e.g., database management system, databaseserver, etc.) configured to receive and process requests for data storedin memory devices of the database(s) and to provide data from thedatabase(s). Database 336 may include NoSQL databases such as HBase,MongoDB™ or Cassandra™. Alternatively, database 336 may includerelational databases such as Oracle, MySQL and Microsoft SQL Server. Insome embodiments, database 336 may take the form of servers, generalpurpose computers, mainframe computers, or any combination of thesecomponents.

Database 336 may store data that may be used by processor 332,respectively, for performing methods and processes associated withdisclosed examples. Database 336 may be located in price determinationsystem 330 as shown in FIG. 3, or alternatively, it may be in externalstorage devices located outside of price determination system 330. Datastored in 336 may include any suitable data associated with products(e.g., age of product, condition of product, inventory rate, status fromreturn center, relationships between age of product and condition ofproduct, relationships between age of product and inventory rate ofproduct, assignments to product identifiers associated with products,historical data of products, the original price of products, discountsto be applied to products, etc.).

User device 320 may be a tablet, mobile device, computer, or the like.User device 320 may include a display. The display may include, forexample, liquid crystal displays (LCD), light emitting diode screens(LED), organic light emitting diode screens (OLED), a touch screen, andother known display devices. The display may show various information toa user. For example, it may display a user interface element, whichincludes an option to scan an indicia (e.g., a barcode, an image, a textstring, an RFID tag, or the like) of a product (e.g., items 202A or 202Bof FIG. 2), to submit a request for assigning a product price to aproduct, to submit a selection of a product or product identifier, tosubmit a pickup request to pick up a returned product from a returncenter and deliver the returned product to FC 200, to submit a requestto list a product for sale (e.g., at a new price), etc. In someembodiments, the display may show historical data of the product (e.g.,previous sales of the product or related products, previous conditionsof the product and whether it was sold at the conditions, the price ordiscount at which the product was sold and the condition associated withthe product for that sale, previous inventory rates of the product andwhether it was sold at the inventory rates, the price or discount atwhich the product was sold and the inventory rate associated with theproduct for that sale, etc.), the original price of a product, adiscount to be applied to a product, a condition of the product, aninventory rate of a product, an age of a product, a “returned” status ofa product, a listing of a product for sale, etc. User device 320 mayinclude one or more input/output (I/O) devices. The I/O devices mayinclude one or more devices that allow user device 320 to send andreceive information from user 320A or another device. The I/O devicesmay include various input/output devices, a camera, a microphone, akeyboard, a mouse-type device, a gesture sensor, an action sensor, aphysical button, an oratory input, etc. The I/O devices may also includeone or more communication modules (not shown) for sending and receivinginformation from price determination system 330 by, for example,establishing wired or wireless connectivity between user device 320 andnetwork 310. In some embodiments, user device 320 may be devices119A-119C of FIG. 1A associated with FC 200.

In some embodiments, user 320A may be an internal user (e.g., employeesof an organization that owns, operates, or leases systems 100 or 300).Internal front end system 105 may be implemented as a computer systemthat enables user 320A to interact with system 300. For example, inembodiments where systems 100 or 300 enable the presentation of systemsto enable users to scan an indicia of a product, submit a request forassigning a product price to a product, submit a selection of a productor product identifier, submit a pickup request to pick up a returnedproduct from a return center and deliver the returned product to FC 200,or submit a request to list a product for sale, internal front endsystem 105 may be implemented as a web server that enables user 320A toview historical data of products, the original prices of products,discounts to be applied to products, conditions of products, inventoryrates of products, ages of products, “returned” statuses of products,listings of products for sale, etc. In some embodiments, internal frontend system 105 may run custom web server software designed to receiveand process requests from systems or devices depicted in systems 100 or300, acquire information from databases (e.g., database 336) and otherdata stores based on those requests, and provide responses to thereceived requests based on acquired information.

In some embodiments, user device 320 may scan an indicia (e.g., abarcode, an image, a text string, an RFID tag, or the like) of a product(e.g., items 202A or 202B of FIG. 2). User device 320 may transmit arequest for assigning a product price to the product to pricedetermination system 330, where the request comprises a productidentifier associated with the product. Price determination system 330may receive the request and based on the received product identifier,price determination system 330 may search database 336 for an originalprice of the product and identify the original price of the product.Price determination system 330 may retrieve the original price of theproduct from database 336.

Price determination system 330 may determine, based on the productidentifier, whether the product is a returned product from a customer.For example, a return center may receive a product returned from acustomer and evaluate the condition of the product. The return centermay determine that the condition of the product is high enough to beresold and may assign a “returned” status to the product based on thedetermination. The return center may be part of or separate from system100. Price determination system 330 may transmit to the return center arequest for a status associated with the product identifier and thereturn center may send a status associated with the product identifierto FC 200 or system 300.

Based on a determination that the product is a returned product from acustomer, price determination system 330 may modify database 336 toassign, to the product identifier, the determination that the product isa returned product. Price determination system 330 may transmit a pickuprequest to a user device associated with a user associated with eitherthe return center or FC 200 (e.g., an inventory worker) to pick up thereturned product from the return center and deliver the returned productto FC 200.

Price determination system 330 may determine a condition of the productbased on the product identifier. For example, the “returned” statusassigned to the product may include a condition of the product. Forexample, the condition of the product may be determined (e.g., by aninternal user, by a system of system 100, etc.) at the return centerbefore the returned product is delivered to FC 200. In some embodiments,the condition may be one of repackaged, package damaged, refurbished,used best, used good, or used normal. A repackaged condition mayindicate that the quality or performance of the product is the same as anew product or only the packaging (e.g., box) may need to be replaced. Apackage damaged condition may indicate that the quality or performanceof the product is the same as a new product or only the packaging may bedamaged, but unopened. A refurbished condition may indicate that theproduct has been used, but a manufacturer or vendor has repaired theproduct so that the quality or performance of the product is high withno problems or missing components. A used best condition may indicatethat the product has been used, but the quality or performance of theproduct is high with no problems or missing components (e.g., like a newproduct). A used good condition may indicate that the product has beenused, but there is only a trace indication of prior product use and theproduct has no problems in performance or missing components. A usednormal condition may indicate that the product has been used and thereis an indication of prior product use, but the product has no problemsin performance.

Price determination system 330 may modify database 336 to assign, to theproduct identifier, the condition of the product and the age of theproduct. Price determination system 330 may determine a new price of theproduct based on the condition of the product and the age of theproduct, where the new price is a discount of the original price. Pricedetermination system 330 may determine the age of the product bydetermining a time duration in which the product is in FC 200 afterdetermining the condition of the product. For example, if a productarrives at FC 200 after price determination system 330 determines acondition of the product on April 1st and today's date is April 11th,then the age of the product is 10 days. For example, price determinationsystem 330 may consult the product identifier stored in database 336 toidentify and access a multi-dimensional data structure. In someembodiments, price determination system 330 may use different accessormethods based on the type of the product (e.g., returned, not returned,etc.). For example, the data structure may quickly access relationshipsbetween the condition of the product and the age of the product based onhistorical data of the product or related products based on the productidentifier. The historical data may include previous sales of theproduct or related products, previous conditions of the product, theprice or discount at which the product was sold and the conditionassociated with the product for that sale, etc. In some embodiments, thedata structure may calculate an optimum discount for the product byaccessing the relationships between the condition of the product and theage of the product. Price determination system 330 may access the datastructure according to the product identifier and determine the newprice of the product based on an optimum discount calculated by the datastructure. The optimum discount may be a discount of the product atwhich the product is most likely to be sold to a customer. In someembodiments, the optimum discount may depend on the seasonality of theproduct or the product webpage view count.

In some embodiments, price determination system 330 may periodicallydetermine the age of unsold products. For example, price determinationsystem 330 may determine that the age of the product has increased by anincrement of time. In some embodiments, the data structure may calculatean optimum discount for the product by accessing the relationshipsbetween the condition of the product and the increased age of theproduct. Based on the product identifier and the determined increment oftime, price determination system 330 may access the data structure todetermine an optimum discount calculated by the data structure andincrease the discount of the original price of the product based on thecalculated optimum discount. For example, price determination system 330may determine that the age of a used best product has increased from 210days to 240 days. Based on the determination that the age of the producthas increased from 210 days to 240 days, price determination system 330may access the data structure and increase the discount of the originalprice of the product from 19% to 21%, which may be calculated by thedata structure. Price determination system 330 may modify database 336to assign the new price to the product identifier and transmit arequest, to user device 320, to list the product for sale at the newprice. In some embodiments, price determination system 330 mayautomatically transmit a notification to a web server (e.g., externalfront end system 103) to list the product for sale at the new price.

Based on a determination that the product is not a returned product froma customer, price determination system 330 may modify database 336 toassign, to the product identifier, the determination that the product isnot a returned product. Price determination system 330 may determine anew price of the product based on the calculated inventory rate, wherethe new price is a discount of the original price. Price determinationsystem 330 may determine the age of the product by determining a timeduration in which the product is in FC 200. For example, if a productarrives at FC 200 on April 1st and today's date is April 11th, then theage of the product is 10 days.

In some embodiments, price determination system 330 may consult theproduct identifier stored in database 336 to identify and access amulti-dimensional data structure. In some embodiments, themulti-dimensional data structure may be the same data structure that isaccessed for returned products. In some embodiments, differentmulti-dimensional data structures may be accessed for returned productsand non-returned products. In some embodiments, price determinationsystem 330 may use different accessor methods based on the type of theproduct (e.g., returned, not returned, etc.). For example, the datastructure may calculate an inventory rate associated with the product.In some embodiments, the data structure may determine a quantity ofusable inventory in all FCs at a national level and calculate an averagedaily sales volume (e.g., average daily number of units sold) during atime span (e.g., the age of the product). In some embodiments, the datastructure may calculate the inventory rate associated with the productby dividing the quantity of usable inventory by the average daily salesvolume.

For example, the data structure may quickly access relationships betweenthe calculated inventory rate and the age of the product based onhistorical data of the product or related products. The historical datamay include previous sales of the product or related products, previousinventory rates of the product, the price or discount at which theproduct was sold and the inventory rate associated with the product forthat sale, etc. In some embodiments, the data structure may calculate anoptimum discount for the product by accessing the relationships betweenthe inventory rate of the product and the age of the product. Pricedetermination system 330 may access the data structure according to theproduct identifier and determine the new price of the product based onan optimum discount calculated by the data structure. The optimumdiscount may be a discount of the product at which the product is mostlikely to be sold to a customer. In some embodiments, the optimumdiscount may depend on the seasonality of the product or the productwebpage view count. Price determination system 330 may modify database336 to assign, to the product identifier, the inventory rate and the newprice.

In some embodiments, price determination system 330 may periodicallydetermine the age of unsold products. For example, price determinationsystem 330 may determine that the age of the product has increased by anincrement of time. In some embodiments, the data structure may calculatean optimum discount for the product by accessing the relationshipsbetween the inventory rate of the product and the increased age of theproduct. Based on the product identifier and the determined increment oftime, price determination system 330 may access the data structure todetermine an optimum discount calculated by the data structure andincrease the discount of the original price of the product based on thecalculated optimum discount. For example, price determination system 330may determine that the age of a product with an inventory rate of 240days has increased from 210 days to 240 days. Based on the determinationthat the age of the product has increased from 210 days to 240 days,price determination system 330 may access the data structure andincrease the discount of the original price of the product from 9% to10%, which may be calculated by the data structure. Price determinationsystem 330 may transmit a request, to user device 320, to list theproduct for sale at the new price. In some embodiments, pricedetermination system 330 may automatically transmit a notification to aweb server (e.g., external front end system 103) to list the product forsale at the new price.

In some embodiments, based on a determination that the discount is lessthan a specific percentage of the original price and a determinationthat the new price is less than a predetermined minimum price, pricedetermination system 330 may modify database 336 to assign thepredetermined minimum price to the product identifier. For example, ifprice determination system 330 determines that the discount is less than10%, then the minimum discount applied to the original price is 50,000

.

In some embodiments, based on a determination that the discount isgreater than a specific percentage of the original price and adetermination that the new price is greater than a predetermined maximumprice, price determination system 330 may modify database 336 to assignthe predetermined maximum price to the product identifier. For example,if price determination system 330 determines that the discount isgreater than 10%, then the maximum discount applied to the originalprice is 100,000

.

In some embodiments, price determination system 330 may determine thatno sales of the product were generated during a time period and based onthe determination, price determination system 330 may increase thediscount of the original price. Price determination system 330 maymodify database 336 to assign an updated price to the productidentifier, where the updated price is the increased discount applied tothe original price. For example, price determination system 330 maydetermine that no sales of the product were generated in the past 360days. Based on this determination, price determination system 330 mayaccess the data structure, increase the discount of the original pricefrom 18% to 20% based on a calculation by the data structure, and modifydatabase 336 to assign an updated price to the product identifier.

In some embodiments, price determination system 330 may periodicallydetermine whether or not discounts should be applied to products and, ifdiscounts should be applied, the value of the discount. For example,price determination system 330 may access a data structure, which maycalculate discounts for products on the first business day of each week.In some embodiments, price determination system 330 may apply a discountto a product based on the category of the product. For example, pricedetermination system 330 may determine that a product belongs to the“book” category, access the data structure, and determine that nodiscounts should be applied to the product.

Referring to FIG. 4, an exemplary multi-dimensional data structure 400that may access relationships between the condition of the product andthe age of the product is shown. As illustrated in FIG. 4, datastructure 400 may calculate discount rates according to relationshipsbetween an age 401 of a product and a condition 403 of the product. Therelationships between the condition of the product and the age of theproduct may be based on historical data of the product or relatedproducts based on the product identifier associated with the product.The historical data may include previous sales of the product or relatedproducts, previous conditions of the product, the price or discount atwhich the product was sold and the condition associated with the productfor that sale, etc. For example, data structure 400 may quickly accessrelationships between condition 403 of the product and age 401 of theproduct based on historical data of the product or related productsbased on the product identifier. In some embodiments, data structure 400may calculate an optimum discount for the product by accessing therelationships between condition 403 of the product and age 401 of theproduct. Price determination system 330 may access data structure 400according to the product identifier and determine the new price of theproduct based on an optimum discount calculated by data structure 400.The optimum discount may be a discount of the product at which theproduct is most likely to be sold to a customer. In some embodiments,the optimum discount may depend on the seasonality of the product or theproduct webpage view count.

Price determination system 330 may determine age 401 of a product bydetermining a time duration in which the product is in FC 200. Forexample, if a product arrives at FC 200 on April 1st and today's date isApril 11th, then the age of the product is 10 days.

Price determination system 330 may determine condition 403 of a productbased on the product identifier associated with the product. Forexample, a “returned” status assigned to the product may include acondition of the product. For example, the condition of the product maybe determined (e.g., by an internal user, by a system of system 100,etc.) at a return center before the returned product is delivered to FC200. The condition may be one of repackaged, package damaged,refurbished, used best, used good, or used normal. A repackagedcondition may indicate that the quality or performance of the product isthe same as a new product or only the packaging (e.g., box) may need tobe replaced. A package damaged condition may indicate that the qualityor performance of the product is the same as a new product or only thepackaging may be damaged, but unopened. A refurbished condition mayindicate that the product has been used, but a manufacturer or vendorhas repaired the product so that the quality or performance of theproduct is high with no problems or missing components. A used bestcondition may indicate that the product has been used, but the qualityor performance of the product is high with no problems or missingcomponents (e.g., like a new product). A used good condition mayindicate that the product has been used, but there is only a traceindication of prior product use and the product has no problems inperformance or missing components. A used normal condition may indicatethat the product has been used and there is an indication of priorproduct use, but the product has no problems in performance.

Price determination system 330 may modify database 336 to assign, to theproduct identifier, age 401 of the product and condition 403 of theproduct. Price determination system 330 may determine a new price of theproduct based on age 401 of the product and condition 403 of theproduct, where the new price is a discount of the original price. Forexample, price determination system 330 may determine that age 401 of aproduct is 120 days and condition 403 of the product is refurbished.Price determination system 330 may consult the product identifier storedin database 336 to identify and access data structure 400. Datastructure 400 may calculate an optimum discount 405 of 13% of theoriginal price of the product by accessing the relationships between age401 of the product and condition 403 of the product. Price determinationsystem 330 may modify database 336 to assign the new price to theproduct identifier and transmit a request, to user device 320, to listthe product for sale at the new price. In some embodiments, pricedetermination system 330 may automatically transmit a notification to aweb server (e.g., external front end system 103) to list the product forsale at the new price.

Although FIG. 4 shows an exemplary data structure 400 of relationshipsbetween age 401 of the product and condition 403 of the product, theembodiments of FIG. 4 are not limited to this specific data structure orspecific relationships and may have other data structures orrelationships as well.

Referring to FIG. 5, an exemplary multi-dimensional data structure 500that may access relationships between the inventory rate of the productand the age of the product is shown. As illustrated in FIG. 5, datastructure 500 may calculate discount rates according to relationshipsbetween an age 501 of a product and an inventory rate 503 of theproduct. The relationships between the inventory rate of the product andthe age of the product may be based on historical data of the product orrelated products based on the product identifier associated with theproduct. The historical data may include previous sales of the productor related products, previous inventory rates of the product, the priceor discount at which the product was sold and the inventory rateassociated with the product for that sale, etc. For example, datastructure 500 may calculate an inventory rate associated with theproduct. In some embodiments, data structure 500 may determine aquantity of usable inventory in all FCs at a national level andcalculate an average daily sales volume (e.g., average daily number ofunits sold) during a time span (e.g., the age of the product). In someembodiments, data structure 500 may calculate the inventory rateassociated with the product by dividing the quantity of usable inventoryby the average daily sales volume. For example, data structure 500 mayquickly access relationships between calculated inventory rate 503 ofthe product and age 501 of the product based on historical data of theproduct or related products based on the product identifier. In someembodiments, data structure 500 may calculate an optimum discount forthe product by accessing the relationships between inventory rate 503 ofthe product and age 501 of the product. Price determination system 330may access data structure 500 according to the product identifier anddetermine the new price of the product based on an optimum discountcalculated by data structure 500. The optimum discount may be a discountof the product at which the product is most likely to be sold to acustomer. In some embodiments, the optimum discount may depend on theseasonality of the product or the product webpage view count.

Price determination system 330 may determine age 501 of a product bydetermining a time duration in which the product is in FC 200. Forexample, if a product arrives at FC 200 on April 1st and today's date isApril 11th, then the age of the product is 10 days.

Price determination system 330 may modify database 336 to assign, to theproduct identifier, age 501 of the product and inventory rate 503 of theproduct. Price determination system 330 may determine a new price of theproduct based on age 501 of the product and inventory rate 503 of theproduct, where the new price is a discount of the original price. Forexample, price determination system 330 may determine that age 501 of aproduct is 120 days and data structure 500 may calculate inventory rate503 of 180 days of the product. Price determination system 330 mayconsult the product identifier stored in database 336 to identify andaccess data structure 500. Data structure 500 may calculate an optimumdiscount 505 of 5% of the original price of the product by accessing therelationships between age 501 of the product and inventory rate 503 ofthe product. Price determination system 330 may modify database 336 toassign the new price to the product identifier and transmit a request,to user device 320, to list the product for sale at the new price. Insome embodiments, price determination system 330 may automaticallytransmit a notification to a web server (e.g., external front end system103) to list the product for sale at the new price.

In some embodiments, the criteria of the discount with respect to therelationships between age 501 of the product and inventory rate 503 ofthe product may be different depending on a status of the product. Insome embodiments, data structure 500 may use different accessor methodsto calculate discounts depending on the different criteria. For example,criteria 507 of the discount may reflect the relationships between age501 and inventory rate 503 for retail products and criteria 509 mayreflect the relationships between age 501 and inventory rate 503 forglobal sourcing products. In some embodiments, retail products andglobal sourcing products may be purchased, operated, or managed by avendor (e.g., a vendor associated with or who owns FC 200). In someembodiments, retail products may be purchased domestically while globalsourcing products may be purchased internationally (e.g., purchased fromoverseas vendors). Retail products and global sourcing products may bedistinguished by indicia (e.g., product identification information). Insome embodiments, data structure 500 may use different accessor methodsto calculate discounts for retail products due to purchase orders andlead times being longer than normal products. Similarly, in someembodiments, data structure 500 may use different accessor methods tocalculate discounts for global sourcing products being purchased inbulk, which may require longer periods of time to sell the products thanfor normal products. The criteria of the discount may vary based on leadtimes, bulk purchases, warehouse arrangements, etc.

Although FIG. 5 shows an exemplary data structure 500 of relationshipsbetween age 501 of the product and inventory rate 503 of the product,the embodiments of FIG. 5 are not limited to this specific datastructure or specific relationships and may have other data structuresor relationships as well.

Referring to FIG. 6, a process 600 for managing inventory by determiningproduct prices based on product characteristics is shown. While in someembodiments price determination system 330 may perform several of thesteps described herein, other implementations are possible. For example,any of the systems and components (e.g., system 100) described andillustrated herein may perform the steps described in this disclosure.

In step 601, user device 320 may scan an indicia (e.g., a barcode, animage, a text string, an RFID tag, or the like) of a product (e.g.,items 202A or 202B of FIG. 2). User device 320 may transmit a requestfor assigning a product price to the product to price determinationsystem 330, where the request comprises a product identifier associatedwith the product.

In step 603, price determination system 330 may receive the request andbased on the received product identifier, price determination system 330may search database 336 for an original price of the product andidentify the original price of the product. Price determination system330 may retrieve the original price of the product from database 336.The original price of a product may be the first price at which theproduct was listed for sale. For example, the original price of areturned product may be the price at which the customer (who returnedthe product) purchased the product. In some embodiments, the originalprice of a non-returned product may be the first price at which theproduct was listed for sale.

In step 605, price determination system 330 may determine, based on theproduct identifier, whether the product is a returned product from acustomer. For example, a return center may receive a product returnedfrom a customer and evaluate the condition of the product. The returncenter may determine that the condition of the product is high enough tobe resold and may assign a “returned” status to the product based on thedetermination. The return center may be part of or separate from system100. Price determination system 330 may transmit to the return center arequest for a status associated with the product identifier and thereturn center may send a status associated with the product identifierto FC 200 or system 300.

In step 607A, based on a determination that the product is a returnedproduct from a customer, price determination system 330 may modifydatabase 336 to assign, to the product identifier, the determinationthat the product is a returned product. Price determination system 330may transmit a pickup request to a user device associated with a userassociated with either the return center or FC 200 (e.g., an inventoryworker) to pick up the returned product from the return center anddeliver the returned product to FC 200.

Price determination system 330 may determine a condition of the productbased on the product identifier. For example, the “returned” statusassigned to the product may include a condition of the product. Forexample, the condition of the product may be determined (e.g., by aninternal user, by a system of system 100, etc.) at the return centerbefore the returned product is delivered to FC 200. The condition may beone of repackaged, package damaged, refurbished, used best, used good,or used normal. A repackaged condition may indicate that the quality orperformance of the product is the same as a new product or only thepackaging (e.g., box) may need to be replaced. A package damagedcondition may indicate that the quality or performance of the product isthe same as a new product or only the packaging may be damaged, butunopened. A refurbished condition may indicate that the product has beenused, but a manufacturer or vendor has repaired the product so that thequality or performance of the product is high with no problems ormissing components. A used best condition may indicate that the producthas been used, but the quality or performance of the product is highwith no problems or missing components (e.g., like a new product). Aused good condition may indicate that the product has been used, butthere is only a trace indication of prior product use and the producthas no problems in performance or missing components. A used normalcondition may indicate that the product has been used and there is anindication of prior product use, but the product has no problems inperformance.

Price determination system 330 may modify database 336 to assign, to theproduct identifier, the condition of the product and the age of theproduct. Price determination system 330 may determine a new price of theproduct based on the condition of the product and the age of theproduct, where the new price is a discount of the original price. Pricedetermination system 330 may determine the age of the product bydetermining a time duration in which the product is in FC 200 afterdetermining the condition of the product. For example, if a productarrives at FC 200 after price determination system 330 determines acondition of the product on April 1st and today's date is April 11th,then the age of the product is 10 days. For example, price determinationsystem 330 may consult the product identifier stored in database 336 toidentify and access a multi-dimensional data structure. In someembodiments, price determination system 330 may use different accessormethods based on the type of the product (e.g., returned, not returned,etc.). For example, the data structure may quickly access relationshipsbetween the condition of the product and the age of the product based onhistorical data of the product or related products based on the productidentifier. The historical data may include previous sales of theproduct or related products, previous conditions of the product, theprice or discount at which the product was sold and the conditionassociated with the product for that sale, etc. In some embodiments, thedata structure may calculate an optimum discount for the product byaccessing the relationships between the condition of the product and theage of the product. Price determination system 330 may access the datastructure according to the product identifier and determine the newprice of the product based on an optimum discount calculated by the datastructure. The optimum discount may be a discount of the product atwhich the product is most likely to be sold to a customer. In someembodiments, the optimum discount may depend on the seasonality of theproduct or the product webpage view count.

Price determination system 330 may modify database 336 to assign the newprice to the product identifier and, in step 609, transmit a request touser device 320 to list the product for sale at the new price. In someembodiments, in step 607, price determination system 330 mayautomatically transmit a notification to a web server (e.g., externalfront end system 103) to list the product for sale at the new price.

In step 607B, based on a determination that the product is not areturned product from a customer, price determination system 330 maymodify database 336 to assign, to the product identifier, thedetermination that the product is not a returned product.

Price determination system 330 may determine a new price of the productbased on the calculated inventory rate, where the new price is adiscount of the original price. Price determination system 330 maydetermine the age of the product by determining a time duration in whichthe product is in FC 200.

In some embodiments, price determination system 330 may consult theproduct identifier stored in database 336 to identify and access amulti-dimensional data structure. In some embodiments, themulti-dimensional data structure may be the same data structure that isaccessed for returned products. In some embodiments, differentmulti-dimensional data structures may be accessed for returned productsand non-returned products. In some embodiments, price determinationsystem 330 may use different accessor methods based on the type of theproduct (e.g., returned, not returned, etc.). For example, the datastructure may calculate an inventory rate associated with the product.In some embodiments, the data structure may determine a quantity ofusable inventory in all FCs at a national level and calculate an averagedaily sales volume (e.g., average daily number of units sold) during atime span (e.g., the age of the product). In some embodiments, the datastructure may calculate the inventory rate associated with the productby dividing the quantity of usable inventory by the average daily salesvolume.

For example, the data structure may quickly access relationships betweenthe calculated inventory rate and the age of the product based onhistorical data of the product or related products. The historical datamay include previous sales of the product or related products, previousinventory rates of the product, the price or discount at which theproduct was sold and the inventory rate associated with the product forthat sale, etc. In some embodiments, the data structure may calculate anoptimum discount for the product by accessing the relationships betweenthe inventory rate of the product and the age of the product. Pricedetermination system 330 may access the data structure according to theproduct identifier and determine the new price of the product based onan optimum discount calculated by the data structure. The optimumdiscount may be a discount of the product at which the product is mostlikely to be sold to a customer. In some embodiments, the optimumdiscount may depend on the seasonality of the product or the productwebpage view count.

Price determination system 330 may modify database 336 to assign, to theproduct identifier, the inventory rate and the new price and, in step609, transmit a request to user device 320 to list the product for saleat the new price. In some embodiments, in step 609, price determinationsystem 330 may automatically transmit a notification to a web server(e.g., external front end system 103) to list the product for sale atthe new price.

While the present disclosure has been shown and described with referenceto particular embodiments thereof, it will be understood that thepresent disclosure can be practiced, without modification, in otherenvironments. The foregoing description has been presented for purposesof illustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. Additionally,although aspects of the disclosed embodiments are described as beingstored in memory, one skilled in the art will appreciate that theseaspects can also be stored on other types of computer readable media,such as secondary storage devices, for example, hard disks or CD ROM, orother forms of RAM or ROM, USB media, DVD, Blu-ray, or other opticaldrive media.

Computer programs based on the written description and disclosed methodsare within the skill of an experienced developer. Various programs orprogram modules can be created using any of the techniques known to oneskilled in the art or can be designed in connection with existingsoftware. For example, program sections or program modules can bedesigned in or by means of .Net Framework, .Net Compact Framework (andrelated languages, such as Visual Basic, C, etc.), Java, C++,Objective-C, HTML, HTML/AJAX combinations, XML, or HTML with includedJava applets.

Moreover, while illustrative embodiments have been described herein, thescope of any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations as would be appreciated bythose skilled in the art based on the present disclosure. Thelimitations in the claims are to be interpreted broadly based on thelanguage employed in the claims and not limited to examples described inthe present specification or during the prosecution of the application.The examples are to be construed as non-exclusive. Furthermore, thesteps of the disclosed methods may be modified in any manner, includingby reordering steps and/or inserting or deleting steps. It is intended,therefore, that the specification and examples be considered asillustrative only, with a true scope and spirit being indicated by thefollowing claims and their full scope of equivalents.

1-20. (canceled)
 21. A computer-implemented system for managinginventory by determining product prices based on productcharacteristics, comprising: one or more memory devices storinginstructions; and one or more processors configured to execute theinstructions to perform operations comprising: determining, based on aproduct identifier, whether a product is a returned product from acustomer; based on a determination that the product is a returnedproduct from a customer: based on at least one of historical data of acondition of the product or a condition of related products, determininga new price of the product; and modifying the database to assign the newprice to the product identifier; based on a determination that theproduct is not a returned product from a customer: based on at least oneof historical data of an inventory rate of the product or an inventoryrate of related products, determining a new price of the product; andmodifying the database to assign, to the product identifier, theinventory rate and the new price; and listing the product for sale atthe new price.
 22. The computer-implemented system of claim 21, whereinwhen the product is a returned product from a customer, determining thenew price of the product comprises determining an age of the product.23. The computer-implemented system of claim 21, wherein when theproduct is a returned product from a customer, determining the new priceof the product comprises determining a condition of the product.
 24. Thecomputer-implemented system of claim 21, wherein when the product is areturned product from a customer, the operations further comprise:determining that an age of the product has increased; and based on thedetermination that the age of the product has increased, increasing adiscount of an original price of the product.
 25. Thecomputer-implemented system of claim 21, wherein when the product is nota returned product from a customer, determining the new price of theproduct comprises determining an age of the product.
 26. Thecomputer-implemented system of claim 21, wherein when the product is nota returned product from a customer, the operations further comprise:determining that an age of the product has increased; and based on thedetermination that the age of the product has increased, increasing adiscount of an original price of the product.
 27. Thecomputer-implemented system of claim 21, wherein determining the newprice of the product comprises calculating an inventory rate associatedwith the product.
 28. The computer-implemented system of claim 21,wherein the new price is a discount of an original price of the productand the operations further comprise: determining that the discount isless than a percentage of the original price; and based on adetermination that the new price is less than a predetermined minimumprice, modifying the database to assign the predetermined minimum priceto the product identifier.
 29. The computer-implemented system of claim21, wherein the new price is a discount of an original price of theproduct and the operations further comprise: determining that thediscount is greater than a percentage of the original price; and basedon a determination that the new price is greater than a predeterminedmaximum price, modifying the database to assign the predeterminedmaximum price to the product identifier.
 30. The computer-implementedsystem of claim 21, wherein the operations further comprise: receiving ascan from a user device associated with a fulfillment center of anindicia of the product; upon receiving the scan from the user device,receiving a request via the user device for assigning a product price tothe product from the user device, wherein the request comprises theproduct identifier associated with the product; and identifying anoriginal price of the product.
 31. A computer-implemented method formanaging inventory by determining product prices based on productcharacteristics, comprising: determining, based on a product identifier,whether a product is a returned product from a customer; based on adetermination that the product is a returned product from a customer:based on at least one of historical data of a condition of the productor a condition of related products, determining a new price of theproduct; and modifying the database to assign the new price to theproduct identifier; based on a determination that the product is not areturned product from a customer: based on at least one of historicaldata of an inventory rate of the product or an inventory rate of relatedproducts, determining a new price of the product; and modifying thedatabase to assign, to the product identifier, the inventory rate andthe new price; and listing the product for sale at the new price. 32.The computer-implemented method of claim 31, wherein when the product isa returned product from a customer, determining the new price of theproduct comprises determining an age of the product.
 33. Thecomputer-implemented method of claim 31, wherein when the product is areturned product from a customer, determining the new price of theproduct comprises determining a condition of the product.
 34. Thecomputer-implemented method of claim 31, wherein when the product is areturned product from a customer, the operations further comprise:determining that an age of the product has increased; and based on thedetermination that the age of the product has increased, increasing adiscount of an original price of the product.
 35. Thecomputer-implemented method of claim 31, wherein when the product is nota returned product from a customer, determining the new price of theproduct comprises determining an age of the product.
 36. Thecomputer-implemented method of claim 31, wherein when the product is nota returned product from a customer and further comprising: determiningthat an age of the product has increased; and based on the determinationthat the age of the product has increased, increasing a discount of anoriginal price of the product.
 37. The computer-implemented method ofclaim 31, wherein determining the new price of the product comprisescalculating an inventory rate associated with the product.
 38. Thecomputer-implemented method of claim 31, wherein the new price is adiscount of an original price of the product and further comprising:determining that the discount is less than a percentage of the originalprice; and based on a determination that the new price is less than apredetermined minimum price, modifying the database to assign thepredetermined minimum price to the product identifier.
 39. Thecomputer-implemented method of claim 31, wherein the new price is adiscount of an original price of the product and further comprising:determining that the discount is greater than a percentage of theoriginal price; and based on a determination that the new price isgreater than a predetermined maximum price, modifying the database toassign the predetermined maximum price to the product identifier. 40.The computer-implemented method of claim 31, further comprising:receiving a scan from a user device associated with a fulfillment centerof an indicia of the product; upon receiving the scan from the userdevice, receiving a request via the user device for assigning a productprice to the product from the user device, wherein the request comprisesthe product identifier associated with the product; and identifying anoriginal price of the product.